-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Input Model Refactor #302
Input Model Refactor #302
Conversation
- Observe property names used for each k8s schemas in k8s schema spec and use them to improve ranking of matched schemas
- Added kafka_crd to test_data/ - Added test case generation code - Partially fixed pylint warnings in test code
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
I personally prefer the name "KubernetesMapSchema" and "KubernetesArraySchema" over "KubernetesDictSchema" and "KubernetesListSchema". As |
@MarkintoshZ , just curious, does the dump_schema method guarantee to persist the original schema's constraints? Just looking at the ObjectSchema it seems it only handles the schemas for each subproperty |
@tylergu It does not currently. In my vision, the testcase generator functions would be provided with (if available) the matched k8s schema object, which stores the Kubernetes schema spec in the On second thought, do we still need to dump schema if each schema file is just part of the OpenAPI schema downloaded from Kubernetes' repo? |
- generator decorator supports k8s schema name, field name, field type, paths, and priority configuration
PR for #296
generator
decorator